Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix release automation #3426

Merged
merged 1 commit into from
Oct 31, 2024

Conversation

m1kola
Copy link
Member

@m1kola m1kola commented Oct 30, 2024

Description of the change:

Our release automation is broken after refactoring in #3280: we are no longer passing a real version number from the release workflow.

Fixes #3419

Architectural changes:

None

Testing remarks:

Need to create a new tag to trigger the workflow

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@jmazzitelli
Copy link
Contributor

You should also delete this file since (a) it doesn't seem to be used anymore and (b) will be confusing

(it currently hasn't been touched in 3 years and has "0.19.0" in it)

https://github.com/operator-framework/operator-lifecycle-manager/blob/master/OLM_VERSION

@m1kola
Copy link
Member Author

m1kola commented Oct 31, 2024

@jmazzitelli I agree with you. I'm planning to look into it, but will probably do that in a separate PR.

kevinrizza
kevinrizza previously approved these changes Oct 31, 2024
@m1kola
Copy link
Member Author

m1kola commented Oct 31, 2024

/hold

Need to fix the release job for non-tag scenarios: docker pull fails because we are attempting to pull quay.io/operator-framework/olm:snapshot which does not exist.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 31, 2024
Signed-off-by: Mikalai Radchuk <[email protected]>
@@ -60,7 +59,8 @@ jobs:
PKG: github.com/operator-framework/operator-lifecycle-manager

- name: Generate quickstart release manifests
run: make release ver=${{ env.IMAGE_TAG }} IMAGE_REPO=quay.io/operator-framework/olm
if: startsWith(github.ref, 'refs/tags')
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this condition back (was removed in #3293). This step pulls an image and we don't have an image when running against anything other than a tag.

@m1kola
Copy link
Member Author

m1kola commented Oct 31, 2024

/unhold

Should be good now

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 31, 2024
@grokspawn grokspawn added this pull request to the merge queue Oct 31, 2024
Merged via the queue into operator-framework:master with commit 5a01f50 Oct 31, 2024
12 checks passed
@m1kola m1kola deleted the fix_release_automation branch November 1, 2024 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0.29.0 never becomes ready
4 participants